Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1984

reference: 212-tree-1
name: 1984
tree-preservation-order: undefined
212-tpo-1
uprn
address-text
point: POINT (-0.942951 50.865347)
geometry: MULTIPOLYGON (((-0.942894 50.865341,-0.942897 50.865352,-0.942905 50.865362,-0.942917 50.865370,-0.942933 50.865375,-0.942950 50.865377,-0.942968 50.865376,-0.942984 50.865371,-0.942997 50.865363,-0.943005 50.865353,-0.943008 50.865342,-0.943005 50.865331,-0.942997 50.865321,-0.942985 50.865312,-0.942969 50.865307,-0.942952 50.865305,-0.942934 50.865307,-0.942918 50.865312,-0.942906 50.865320,-0.942897 50.865330,-0.942894 50.865341)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL